Tool Mentor: Analyzing Automatically Generated Test Scripts Using Rational TestFactory^TM, Rational Robot^TM, and the Rational LogViewer^TM

Purpose

This tool mentor describes how to use Rational TestFactory, Rational Robot, and the Rational LogViewer to analyze automatically generated test scripts that uncovered errors.

Related Rational Unified Process activities:

• Section "Evaluate Execution of Test" of Activity: Execute Test

Overview

This Tool Mentor is applicable when running Windows 95/98/2000/NT 4.0.

To use TestFactory, Robot, and the LogViewer to analyze the automatically generated test scripts, do one or both of the following:

• Analyze a test script that uncovered a defect.
• Analyze a test script that uncovered an unexpected active window.

ò  Analyze a test script that uncovered a defect

As described in Tool Mentor: Generating Test Scripts Automatically Using Rational TestFactory, a Pilot is the TestFactory tool that automatically generates test scripts. For each defect it encounters while it is running, a Pilot generates a ôdefect script,ö which contains the script statements that cause the defect to occur.

When a Pilot finds defects during the run, the test scripts that uncovered defects are located in a separate ôDefects Foundö subfolder under the run folder. You can use the LogViewer to view the run log for the test scripts that uncovered defects.

   Refer to the following topic in TestFactory Help:

• View the log for a script run

For details on analyzing a test script in the LogViewer, see Tool Mentor: Evaluating Execution of Test Using the Rational LogViewer.

ò  Analyze a test script that uncovered an unexpected active window

During test script generation, a Pilot can encounter an ôunexpected active windowö (UAW)ùa window that reflects an inconsistency between the UI objects in the application map and the controls in the application-under-test (AUT). One of two conditions can cause the Pilot to encounter an unexpected active window:

• The AUT contains a window for which there is no corresponding UI object in the application map. A typical example of this condition is a message window that is not uncovered during mapping.
• A UI object in the application map represents a window that is no longer in the AUT.

Whenever it encounters an unexpected active window, the Pilot generates a ôUAW scriptö and places it in the Pilot run folder. You can play back a UAW script in Robot, and then use Robot and the LogViewer to determine the cause of the unexpected active window. After you resolve the cause in TestFactory, subsequent Pilot runs will not encounter the unexpected active window.

   Refer to the following topics in TestFactory Help:

• Find the cause of an unexpected active window
• Resolve an unexpected active window

Rational Unified Process